Skip to content

Conversation

@hexfusion
Copy link
Contributor

@hexfusion hexfusion commented Mar 11, 2019

This PR adds the newly built kube-client-agent image registry.svc.ci.openshift.org/openshift/origin-v4.0:kube-client-agent replacing the coreos/kubecsr upstream.

Because of chicken and egg I need to set the default to pass tests and will update this after the flag is added to installer.

@openshift-ci-robot openshift-ci-robot added the size/M Denotes a PR that changes 30-99 lines, ignoring generated files. label Mar 11, 2019
@hexfusion
Copy link
Contributor Author

updating test yamls

@hexfusion
Copy link
Contributor Author

/test images

@kikisdeliveryservice
Copy link
Contributor

hi @hexfusion !

Could you update the commit message to include (in the body): after related flag PR merged into installer, uncomment bootstrapCmd.MarkFlagRequired("kube-client-agent-image") in bootstrap.go

@hexfusion
Copy link
Contributor Author

@kikisdeliveryservice sure thing all set.

@kikisdeliveryservice
Copy link
Contributor

thanks @hexfusion !!

@hexfusion hexfusion force-pushed the fx_kubecsr branch 3 times, most recently from 70e063d to a10801b Compare March 11, 2019 21:26
@openshift-ci-robot openshift-ci-robot added the needs-rebase Indicates a PR cannot be merged because it has merge conflicts with HEAD. label Mar 13, 2019
@openshift-ci-robot openshift-ci-robot removed the needs-rebase Indicates a PR cannot be merged because it has merge conflicts with HEAD. label Mar 13, 2019
@hexfusion
Copy link
Contributor Author

/retest

@hexfusion
Copy link
Contributor Author

/test images

1 similar comment
@hexfusion
Copy link
Contributor Author

/test images

@hexfusion
Copy link
Contributor Author

/retest

@hexfusion
Copy link
Contributor Author

/retest

@hexfusion
Copy link
Contributor Author

removing default for testing release.

@cgwalters
Copy link
Member

Oh man this again...luckily the scars are fresh from the last time:
#471

It looks like you probably saw #471 (comment) at least?

@hexfusion
Copy link
Contributor Author

@cgwalters @abhinavdahiya with the above PR and installer with openshift/installer#1401 it works can we force 1401? then this?

To confirm my test actions I did the following which was the latest ci release on this PR. My installer as noted contains openshift/installer#1401

OPENSHIFT_INSTALL_RELEASE_IMAGE_OVERRIDE=registry.svc.ci.openshift.org/ci-op-gmkb8pn6/release:latest openshift-install-dev --log-level debug --dir aws-cluster/cluster-dev create cluster

@abhinavdahiya
Copy link
Contributor

abhinavdahiya commented Mar 14, 2019

@cgwalters @abhinavdahiya with the above PR and installer with openshift/installer#1401 it works can we force 1401? then this?

To confirm my test actions I did the following which was the latest ci release on this PR. My installer as noted contains openshift/installer#1401

OPENSHIFT_INSTALL_RELEASE_IMAGE_OVERRIDE=registry.svc.ci.openshift.org/ci-op-gmkb8pn6/release:latest openshift-install-dev --log-level debug --dir aws-cluster/cluster-dev create cluster

The way you can proceed without force is:

  1. in This PR
  • hard code the image to registry one here, do not use the one set by flag.
  • hard code the image to registry one here, do not use the one set in config map.
  1. This allows installer PR Bug 1684670: data/data/bootstrap: add kube-client-agent-image flag installer#1401 to set set the flag,

  2. come and switch here and here to use the correct images from flag and config map. And also set the flag as required.

This way the images always stay the same.

@hexfusion
Copy link
Contributor Author

Ci failure unrelated I just ran OPENSHIFT_INSTALL_RELEASE_IMAGE_OVERRIDE=registry.svc.ci.openshift.org/ci-op-0xsz8z88/release:latest with success.

level=error msg="Error: Error applying plan:"
level=error
level=error msg="4 errors occurred:"
level=error msg="\t* module.vpc.aws_route_table_association.route_net[1]: 1 error occurred:"
level=error msg="\t* aws_route_table_association.route_net.1: timeout while waiting for state to become 'success' (timeout: 5m0s)"
level=error
level=error
level=error msg="\t* module.vpc.aws_route_table_association.route_net[0]: 1 error occurred:"
level=error msg="\t* aws_route_table_association.route_net.0: timeout while waiting for state to become 'success' (timeout: 5m0s)"
level=error
level=error
level=error msg="\t* module.vpc.aws_route_table_association.route_net[3]: 1 error occurred:"
level=error msg="\t* aws_route_table_association.route_net.3: timeout while waiting for state to become 'success' (timeout: 5m0s)"
level=error
level=error
level=error msg="\t* module.vpc.aws_route_table_association.route_net[4]: 1 error occurred:"
level=error msg="\t* aws_route_table_association.route_net.4: timeout while waiting for state to become 'success' (timeout: 5m0s)"
level=error

@hexfusion
Copy link
Contributor Author

/retest

@hexfusion
Copy link
Contributor Author

/test e2e-aws

@hexfusion
Copy link
Contributor Author

@abhinavdahiya PTAL this will pass if we can leap over resource limit.

@abhinavdahiya
Copy link
Contributor

@abhinavdahiya PTAL this will pass if we can leap over resource limit.

LGTM

- after related flag PR merged into installer, uncomment bootstrapCmd.MarkFlagRequired("kube-client-agent-image") in bootstrap.go

Signed-off-by: Sam Batschelet <sbatsche@redhat.com>
@hexfusion
Copy link
Contributor Author

/retest

@hexfusion
Copy link
Contributor Author

/test e2e-aws

@hexfusion
Copy link
Contributor Author

/cc @cgwalters @kikisdeliveryservice

@runcom
Copy link
Member

runcom commented Mar 15, 2019

/approve
/lgtm

@openshift-ci-robot openshift-ci-robot added the lgtm Indicates that a PR is ready to be merged. label Mar 15, 2019
@openshift-ci-robot
Copy link
Contributor

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: hexfusion, runcom

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Details Needs approval from an approver in each of these files:

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@openshift-ci-robot openshift-ci-robot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Mar 15, 2019
@hexfusion
Copy link
Contributor Author

/test e2e-aws-op

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

approved Indicates a PR has been approved by an approver from all required OWNERS files. lgtm Indicates that a PR is ready to be merged. size/M Denotes a PR that changes 30-99 lines, ignoring generated files.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

7 participants